Generally, you need to walk through these procedures only once, when first setting up the servers and clients to be used in your implementation.
To prepare database server hosts
1. Verify that each server to host an iMIS database meets all system requirements.
2. (new installs) Verify that the SQL Server instance where the new iMIS database will be created is configured to use a SQL collation of sort order ID 52.
The SQL Server instance must not be a mixed-collation environment. When you install a new iMIS database, your instance must have a default SQL collation of SQL_Latin1_General_CP1_CI (sort order ID 52), which is the default for the EmptyDB and DemoDB provided with iMIS. If your SQL Server default is different, reinstall SQL Server with the correct collation before installing iMIS.
To prepare application and web server hosts
Tip: The installer warns you if it cannot enable or detect a required service. See Troubleshooting services for how iMIS needs services to be configured.
1. Verify that each server host meets all system requirements.
2. Windows 2003: Install SP2, or the process will fail.
3. (upgrades) (Application servers only) Update your current installation of iMIS to required release levels and licensing: iMIS must be at 15.1.3 or higher.
4. Verify that you can make a SQL connection from each iMIS server host to the SQL Server instance on the database host where the iMIS database resides.
To prepare workstations
1. Verify that each user workstation meets all system requirements for the type of client to be used.
2. (iMIS Desktop) Verify that a high-bandwidth (10/100) SQL connection can be made between workstations and the SQL Server instance hosting the iMIS database.
Tip: Avoid low-bandwidth connections to the database host (such as via VPN): the high-volume SQL traffic will slow performance for iMIS Desktop users. If you have remote staff who need Desktop, have them run it from a terminal server that is on the same network as the database host.
3. Optimize Internet Explorer settings for iMIS.
□ (if running iMIS Desktop on Windows Server) In Manager Your Server (2003) or Server Manager (2008), go to Internet Explorer Enhanced Security Configuration (Configure IE ESC) and disable both Administrators and Users. (Expect IE to warn you that this is disabled.)
□ In Internet Explorer, select Tools > Internet Options.
□ On the General tab, select Browsing History Settings. Under Temporary Internet Files, set Check for newer versions of stored pages to Every time I visit the webpage.
□ On the Security tab, select Trusted Sites, and set the Security Level to Low.
□ With Trusted Sites still selected, click Sites, add the name of your iMIS application server host (http://myserver), disable Require server verification (https:) if not using SSL, and select Close.
□ On the Advanced tab, check Disable script debugging (other), and select OK.
4. (Analytics) Ensure that each workstation that will be using ProClarity Pro to view the Analytics analysis database can address the Analytics host (where the data warehouse and analysis database are installed) by using a standard computer name.
Note: Using ProClarity Professional on a remotely accessed Terminal Server or Citrix machine is untested. VPN connections from ProClarity Professional on a workstation to the domain containing the Analytics host is also untested.